You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a result, in the face of a malicious request whose Authorization header consists of Bearer followed by many period characters, a call to that function incurs allocations to the tune of O(n) bytes (where n stands for the length of the function's argument), with a constant factor of about 16. Relevant weakness: CWE-405: Asymmetric Resource Consumption (Amplification)
Review comments: Directly reply to a review comment made by CodeRabbit. Example:
I pushed a fix in commit <commit_id>, please review it.
Generate unit testing code for this file.
Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
@coderabbitai generate unit testing code for this file.
@coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
@coderabbitai read src/utils.ts and generate unit testing code.
@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
@coderabbitai help me debug CodeRabbit configuration file.
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.
CodeRabbit Commands (Invoked using PR comments)
@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
Documentation and Community
Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.
renovateBot
changed the title
fix(deps): update module github.com/golang-jwt/jwt/v5 to v5.2.2 [security]
fix(deps): update module github.com/golang-jwt/jwt/v5 to v5.2.2 [security] - autoclosed
May 12, 2025
renovateBot
deleted the
renovate/go-github.com-golang-jwt-jwt-v5-vulnerability
branch
May 12, 2025 06:09
renovateBot
changed the title
fix(deps): update module github.com/golang-jwt/jwt/v5 to v5.2.2 [security] - autoclosed
fix(deps): update module github.com/golang-jwt/jwt/v5 to v5.2.2 [security]
May 12, 2025
renovateBot
changed the title
fix(deps): update module github.com/golang-jwt/jwt/v5 to v5.2.2 [security]
fix(deps): update module github.com/golang-jwt/jwt/v5 to v5.2.2 [security] - autoclosed
Mar 27, 2026
renovateBot
changed the title
fix(deps): update module github.com/golang-jwt/jwt/v5 to v5.2.2 [security] - autoclosed
fix(deps): update module github.com/golang-jwt/jwt/v5 to v5.2.2 [security]
Mar 30, 2026
renovateBot
changed the title
fix(deps): update module github.com/golang-jwt/jwt/v5 to v5.2.2 [security]
Update module github.com/golang-jwt/jwt/v5 to v5.2.2 [SECURITY]
Apr 8, 2026
renovateBot
changed the title
Update module github.com/golang-jwt/jwt/v5 to v5.2.2 [SECURITY]
Update module github.com/golang-jwt/jwt/v5 to v5.2.2 [SECURITY] - autoclosed
May 11, 2026
renovateBot
changed the title
Update module github.com/golang-jwt/jwt/v5 to v5.2.2 [SECURITY] - autoclosed
Update module github.com/golang-jwt/jwt/v5 to v5.2.2 [SECURITY]
May 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v5.2.1→v5.2.2jwt-go allows excessive memory allocation during header parsing
CVE-2025-30204 / GHSA-mh63-6h87-95cp
More information
Details
Summary
Function
parse.ParseUnverifiedcurrently splits (via a call to strings.Split) its argument (which is untrusted data) on periods.As a result, in the face of a malicious request whose Authorization header consists of
Bearerfollowed by many period characters, a call to that function incurs allocations to the tune of O(n) bytes (where n stands for the length of the function's argument), with a constant factor of about 16. Relevant weakness: CWE-405: Asymmetric Resource Consumption (Amplification)Details
See
parse.ParseUnverifiedImpact
Excessive memory allocation
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
golang-jwt/jwt (github.com/golang-jwt/jwt/v5)
v5.2.2Compare Source
What's Changed
jwt.Parseexample to usejwt.WithValidMethodsby @mattt in #425New Contributors
Full Changelog: golang-jwt/jwt@v5.2.1...v5.2.2
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.